partial hydration
Rendering on the Web
#WIP
Progressive hydrationを拡張したもの
This approach is an extension of the idea of progressive rehydration, where the individual pieces (components / views / trees) to be progressively rehydrated are analyzed and those with little interactivity or no reactivity are identified. For each of these mostly-static parts, the corresponding JavaScript code is then transformed into inert references and decorative functionality, reducing their client-side footprint to near-zero. The partial hydration approach comes with its own issues and compromises. It poses some interesting challenges for caching, and client-side navigation means we can't assume server-rendered HTML for inert parts of the application will be available without a full page load. ref
ほぼほぼ何を言っているのかわからん #??
inert referencesとdecorative functionalityってなに
https://en.wikipedia.org/wiki/Hydration_(web_development)#Partial_rehydration
https://elderguide.com/tech/elderjs/#:~:text=as%20defined%20below.-,Partial%20Hydration,-Elder.js%20give
https://ajcwebdev.com/what-is-partial-hydration-and-why-is-everyone-talking-about-it
https://zenn.dev/qrac/articles/b9c65c1c0be901
Elder.js
Qwik